Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The application must implement transaction recovery logs when transaction based.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-69441 | APSC-DV-001040 | SV-84063r1_rule | Medium |
| Description |
|---|
| Without required logging and access control, security issues related to data changes will not be identified. This could lead to security compromises such as data misuse, unauthorized changes, or unauthorized access. Transaction logs contain a sequential record of all changes to the database. Using a transaction log helps with maintaining application availability and aids in speedy recovery. Transactional logging should be enabled whenever the application database offers the transactional logging capability. |
| STIG | Date |
|---|---|
| Application Security and Development Security Technical Implementation Guide | 2017-03-20 |
Details
| Check Text ( C-69859r1_chk ) |
|---|
| Review the application documentation and interview the application administrator. Have the application administrator provide configuration settings that demonstrate transaction logging is enabled. Review configuration settings for the location of transaction specific logs and verify transaction logs exist and the log records access and changes to the data. If the application is not configured to utilize transaction logging, this is a finding. |
| Fix Text (F-75617r1_fix) |
|---|
| Configure the application database to utilize transactional logging. |